Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0a15e991b1fd60ba76a7cea5453e0888f5753e544e223206861297090a64f64

Tx prefix hash: 31855126a3298f5618b1994e797562d4abbc37a810e05c656e4dec0053c63992
Tx public key: 8df6cfaa75a700281f66a6e4ea26233e72c7b709441716667d416e619b7f5810
Timestamp: 1721143090 Timestamp [UCT]: 2024-07-16 15:18:10 Age [y:d:h:m:s]: 00:178:14:42:28
Block: 1067043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127791 RingCT/type: yes/0
Extra: 018df6cfaa75a700281f66a6e4ea26233e72c7b709441716667d416e619b7f581002110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5aa73abf04232292d43e4df4f2d28e4f7c11dccc097b906dd2f898bdefb2b13a 0.600000000000 1537752 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": 1067053, "vin": [ { "gen": { "height": 1067043 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5aa73abf04232292d43e4df4f2d28e4f7c11dccc097b906dd2f898bdefb2b13a" } } ], "extra": [ 1, 141, 246, 207, 170, 117, 167, 0, 40, 31, 102, 166, 228, 234, 38, 35, 62, 114, 199, 183, 9, 68, 23, 22, 102, 125, 65, 110, 97, 155, 127, 88, 16, 2, 17, 0, 0, 0, 4, 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