Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e12239cbc272375e1cf4fc41a259e098c359afddabdd3b4edbf2030ce37c9e2f

Tx prefix hash: 8e70d9dafa7da3317c553c5a27ae14df6fccc775bf364505ffcf4933d92321b9
Tx public key: b0f594246fa9a2f9023bbf97313c353d11d6b8d15f0f6d5ae0362ac8232d55c7
Timestamp: 1731947870 Timestamp [UCT]: 2024-11-18 16:37:50 Age [y:d:h:m:s]: 00:135:22:07:17
Block: 1156509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96963 RingCT/type: yes/0
Extra: 01b0f594246fa9a2f9023bbf97313c353d11d6b8d15f0f6d5ae0362ac8232d55c7021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f64a8ec3de56c93e7a13e888dd9103d98da00b000112a38497769a02a1caa14a 0.600000000000 1642132 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": 1156519, "vin": [ { "gen": { "height": 1156509 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f64a8ec3de56c93e7a13e888dd9103d98da00b000112a38497769a02a1caa14a" } } ], "extra": [ 1, 176, 245, 148, 36, 111, 169, 162, 249, 2, 59, 191, 151, 49, 60, 53, 61, 17, 214, 184, 209, 95, 15, 109, 90, 224, 54, 42, 200, 35, 45, 85, 199, 2, 17, 0, 0, 0, 1, 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