Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 357018aa36d451a1bf3df5614e2829d019eb9ebad4f4e7e59c8519821b0da12f

Tx prefix hash: 3c622e2c563acc6c77bece7912f1c562d85d3455f15132a29eaf84963bb04be4
Tx public key: 80e9b7664a99b0f4ba3de4f1fdbf1d97875ad786cd3601d455162884ab318f63
Timestamp: 1714185680 Timestamp [UCT]: 2024-04-27 02:41:20 Age [y:d:h:m:s]: 01:040:05:09:07
Block: 1009339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289719 RingCT/type: yes/0
Extra: 0180e9b7664a99b0f4ba3de4f1fdbf1d97875ad786cd3601d455162884ab318f6302110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c27f2cc834bfb73776b61f8336920c596aa65e62e3fa3a01ffafdbafbcdad2d8 0.600000000000 1470985 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": 1009349, "vin": [ { "gen": { "height": 1009339 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c27f2cc834bfb73776b61f8336920c596aa65e62e3fa3a01ffafdbafbcdad2d8" } } ], "extra": [ 1, 128, 233, 183, 102, 74, 153, 176, 244, 186, 61, 228, 241, 253, 191, 29, 151, 135, 90, 215, 134, 205, 54, 1, 212, 85, 22, 40, 132, 171, 49, 143, 99, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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