Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f68fdea09c7fb5bf78b869d1de16ab1662c9f81958fa6567877b7b390c303964

Tx prefix hash: 672a865ab03557e91531d0584e14dc21cadebb89722ada0e075a90800c588f26
Tx public key: 60bf8a952c8accdf999710ae8fdf5d0b4e954daefe05df35f0a065323ad407f3
Timestamp: 1729039004 Timestamp [UCT]: 2024-10-16 00:36:44 Age [y:d:h:m:s]: 00:209:23:12:39
Block: 1132514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149851 RingCT/type: yes/0
Extra: 0160bf8a952c8accdf999710ae8fdf5d0b4e954daefe05df35f0a065323ad407f3021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 158dc0f4d127e516c666a701feda3a69a185faf869dbeb041b84709b325ad140 0.600000000000 1615441 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": 1132524, "vin": [ { "gen": { "height": 1132514 } } ], "vout": [ { "amount": 600000000, "target": { "key": "158dc0f4d127e516c666a701feda3a69a185faf869dbeb041b84709b325ad140" } } ], "extra": [ 1, 96, 191, 138, 149, 44, 138, 204, 223, 153, 151, 16, 174, 143, 223, 93, 11, 78, 149, 77, 174, 254, 5, 223, 53, 240, 160, 101, 50, 58, 212, 7, 243, 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