Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 836aa309ab11b6831c9b6f7218b2713699b494b5e6c5a01cb056e2840607b373

Tx prefix hash: 27ba776dc9a067d2a84f5ad92b9cc02d1a46e284be278f5d21aa84c30f7d1585
Tx public key: 7063617d078c4019c5008e63e57610ec430e3bf9cb0a39f7838f424fcfb45abe
Timestamp: 1723295665 Timestamp [UCT]: 2024-08-10 13:14:25 Age [y:d:h:m:s]: 00:220:20:43:26
Block: 1084881 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157748 RingCT/type: yes/0
Extra: 017063617d078c4019c5008e63e57610ec430e3bf9cb0a39f7838f424fcfb45abe02110000000c91e13c04000000000000000000

1 output(s) for total of 0.615580000000 dcy

stealth address amount amount idx
00: 0d4fcb9ef090a475f259a5b22f8d26b94522994d51a6d0a686e18ef7ac711fb1 0.615580000000 1559312 of 0

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": 1084891, "vin": [ { "gen": { "height": 1084881 } } ], "vout": [ { "amount": 615580000, "target": { "key": "0d4fcb9ef090a475f259a5b22f8d26b94522994d51a6d0a686e18ef7ac711fb1" } } ], "extra": [ 1, 112, 99, 97, 125, 7, 140, 64, 25, 197, 0, 142, 99, 229, 118, 16, 236, 67, 14, 59, 249, 203, 10, 57, 247, 131, 143, 66, 79, 207, 180, 90, 190, 2, 17, 0, 0, 0, 12, 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