Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb61efb54afce7222c13dd02261ea901b46e46ca60083b0d0120f2584ad0e3cd

Tx prefix hash: f55e3daf66db756c516ff418737862b168659bb942c15b458160581872e543e5
Tx public key: 9c0e9d2c45d8c09093be4919f25005c0d764729a87d1890b510dce314e738b0f
Timestamp: 1731725189 Timestamp [UCT]: 2024-11-16 02:46:29 Age [y:d:h:m:s]: 00:360:20:17:40
Block: 1154682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255426 RingCT/type: yes/0
Extra: 019c0e9d2c45d8c09093be4919f25005c0d764729a87d1890b510dce314e738b0f021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32dfb1f222f89f760b53ac18c623a473f5e22da237c053e27a707e1cb12ddad6 0.600000000000 1640295 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": 1154692, "vin": [ { "gen": { "height": 1154682 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32dfb1f222f89f760b53ac18c623a473f5e22da237c053e27a707e1cb12ddad6" } } ], "extra": [ 1, 156, 14, 157, 44, 69, 216, 192, 144, 147, 190, 73, 25, 242, 80, 5, 192, 215, 100, 114, 154, 135, 209, 137, 11, 81, 13, 206, 49, 78, 115, 139, 15, 2, 17, 0, 0, 0, 4, 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