Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 4d40c406dbb2be37ca97bf9c142dc19773145b9cfbd743a8d88a1b7c0f8b1571

Tx prefix hash: f76a6dcb80e23b20ef28f141fef8902ffd2da197790842bb55b91507b42f042d
Tx public key: 931a84a079f1fd54b7d1cdedef0c2e175c8ae32a6dc9c64a3fe9aefd4ce7b6bd
Timestamp: 1726186740 Timestamp [UCT]: 2024-09-13 00:19:00 Age [y:d:h:m:s]: 01:083:04:15:30
Block: 1108841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317913 RingCT/type: yes/0
Extra: 01931a84a079f1fd54b7d1cdedef0c2e175c8ae32a6dc9c64a3fe9aefd4ce7b6bd021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 58b3d00376816d4e089640d504929dacecaef95032377a5f4597cd8bae74aad6 0.600000000000 1586886 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1108851, "vin": [ { "gen": { "height": 1108841 } } ], "vout": [ { "amount": 600000000, "target": { "key": "58b3d00376816d4e089640d504929dacecaef95032377a5f4597cd8bae74aad6" } } ], "extra": [ 1, 147, 26, 132, 160, 121, 241, 253, 84, 183, 209, 205, 237, 239, 12, 46, 23, 92, 138, 227, 42, 109, 201, 198, 74, 63, 233, 174, 253, 76, 231, 182, 189, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8