Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01e60cc8b4d584d35274d2cf246e48bf405ae573203afe2805987e4341a2a8d0

Tx prefix hash: 75842a6c1338bf315547a4dd2dd8a4b9023ef908f16d0c3e4b155ab2e2637f1b
Tx public key: 857e3c782000e1a89f4dfd9586980f26218391f480bb29ddfd9cdcd90feaf95d
Timestamp: 1728838586 Timestamp [UCT]: 2024-10-13 16:56:26 Age [y:d:h:m:s]: 00:223:07:35:47
Block: 1130831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159429 RingCT/type: yes/0
Extra: 01857e3c782000e1a89f4dfd9586980f26218391f480bb29ddfd9cdcd90feaf95d02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5f80cf234edb2924b0d6c32f2158811fb9592c8fceb113230c6b2aedcbb4a52 0.600000000000 1613712 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": 1130841, "vin": [ { "gen": { "height": 1130831 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5f80cf234edb2924b0d6c32f2158811fb9592c8fceb113230c6b2aedcbb4a52" } } ], "extra": [ 1, 133, 126, 60, 120, 32, 0, 225, 168, 159, 77, 253, 149, 134, 152, 15, 38, 33, 131, 145, 244, 128, 187, 41, 221, 253, 156, 220, 217, 15, 234, 249, 93, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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