Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d218af053e31575a94fcd44cd812304acd91e6e2bca0036c0044ff582f60527e

Tx prefix hash: f3e77c325b0239ab4b330f94e88128cee0deb864c085d91202fb77d23c1eb84b
Tx public key: eb9143d2e9c005c0eaa08317544438c7593c16e1d8f5f20e8738cfd3b39688fe
Timestamp: 1766619992 Timestamp [UCT]: 2025-12-24 23:46:32 Age [y:d:h:m:s]: 00:013:13:53:38
Block: 1440914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9735 RingCT/type: yes/0
Extra: 01eb9143d2e9c005c0eaa08317544438c7593c16e1d8f5f20e8738cfd3b39688fe02110000000234af31cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66565d60ef15913f2b83a8cf8d625d005c5fcb49f4b1b1862dcb3b19163514ab 0.600000000000 1929805 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": 1440924, "vin": [ { "gen": { "height": 1440914 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66565d60ef15913f2b83a8cf8d625d005c5fcb49f4b1b1862dcb3b19163514ab" } } ], "extra": [ 1, 235, 145, 67, 210, 233, 192, 5, 192, 234, 160, 131, 23, 84, 68, 56, 199, 89, 60, 22, 225, 216, 245, 242, 14, 135, 56, 207, 211, 179, 150, 136, 254, 2, 17, 0, 0, 0, 2, 52, 175, 49, 204, 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