Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3d04fca206d75833602181b4959a44bd68c75462f6564cea9297e3b5b2db10e

Tx prefix hash: 2c7b5680812b092a6526fe2c0f64ad38d7f54ba41eec4bcd32a2132e4f016c29
Tx public key: ace5e3f056e5a96dcbf52e0d4e451289e9b2983fb33ab6c9c23cd4af42e1dd14
Timestamp: 1695545189 Timestamp [UCT]: 2023-09-24 08:46:29 Age [y:d:h:m:s]: 02:044:10:55:20
Block: 855008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 551411 RingCT/type: yes/0
Extra: 01ace5e3f056e5a96dcbf52e0d4e451289e9b2983fb33ab6c9c23cd4af42e1dd140211000000054b8f5122000000000000000000

1 output(s) for total of 0.901578641000 dcy

stealth address amount amount idx
00: 8363ffd0ed95ce60d2dfd7c63030a096de127ca21d84a5dc6e02113805409964 0.901578641000 1309006 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": 855018, "vin": [ { "gen": { "height": 855008 } } ], "vout": [ { "amount": 901578641, "target": { "key": "8363ffd0ed95ce60d2dfd7c63030a096de127ca21d84a5dc6e02113805409964" } } ], "extra": [ 1, 172, 229, 227, 240, 86, 229, 169, 109, 203, 245, 46, 13, 78, 69, 18, 137, 233, 178, 152, 63, 179, 58, 182, 201, 194, 60, 212, 175, 66, 225, 221, 20, 2, 17, 0, 0, 0, 5, 75, 143, 81, 34, 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