Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3d85ccf947dba4c9cb907c5cbe635eb2236f8e90241d73d4a51c8be5de7036e

Tx prefix hash: 5af9460a12439088c7a6ec959562cc564af5ac5be3f28c609fa00282d68ddfca
Tx public key: 1d28ed32a8f8025db297271ef6a5663c7832b16ae7b180324d7c1a1954741a20
Timestamp: 1726874296 Timestamp [UCT]: 2024-09-20 23:18:16 Age [y:d:h:m:s]: 00:195:23:06:36
Block: 1114545 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139874 RingCT/type: yes/0
Extra: 011d28ed32a8f8025db297271ef6a5663c7832b16ae7b180324d7c1a1954741a200211000000015a5c538d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d54ed1a903e4177e7ea3d13684b6a3608e6372f0135be43b48f3a560023a7fc8 0.600000000000 1594362 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": 1114555, "vin": [ { "gen": { "height": 1114545 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d54ed1a903e4177e7ea3d13684b6a3608e6372f0135be43b48f3a560023a7fc8" } } ], "extra": [ 1, 29, 40, 237, 50, 168, 248, 2, 93, 178, 151, 39, 30, 246, 165, 102, 60, 120, 50, 177, 106, 231, 177, 128, 50, 77, 124, 26, 25, 84, 116, 26, 32, 2, 17, 0, 0, 0, 1, 90, 92, 83, 141, 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