Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6181086976424b1636ec5073b0d9f9ef17f1edc817b00320d528a67a9160115c

Tx prefix hash: 0a72f266d0e7dfb6c1c4acff91d84ac7ac86c9c14830b8fa7f5734e33e70d6f1
Tx public key: 72a74c5abdff303357cfe639f3c3fa3f9b14ba5863d059b6752c61bab73fecad
Timestamp: 1740329862 Timestamp [UCT]: 2025-02-23 16:57:42 Age [y:d:h:m:s]: 00:226:16:58:01
Block: 1225630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159730 RingCT/type: yes/0
Extra: 0172a74c5abdff303357cfe639f3c3fa3f9b14ba5863d059b6752c61bab73fecad021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd62cc53c2aac9ef497114d38549ba56fbc3a89d18838e2b7aa2ef7891f658b5 0.600000000000 1712497 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": 1225640, "vin": [ { "gen": { "height": 1225630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd62cc53c2aac9ef497114d38549ba56fbc3a89d18838e2b7aa2ef7891f658b5" } } ], "extra": [ 1, 114, 167, 76, 90, 189, 255, 48, 51, 87, 207, 230, 57, 243, 195, 250, 63, 155, 20, 186, 88, 99, 208, 89, 182, 117, 44, 97, 186, 183, 63, 236, 173, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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