Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a929a5bf00aebbd96e730f210ccf5c6b5747e700de62de16e15a52b09b3f1587

Tx prefix hash: 87cf91062670f458716c374ed2ad8b67c76696e40e37d672cea62e1c47e060fd
Tx public key: 659c313a15e0d210e567c63ac4ecb216848f96b747adf23c77272739fe4e04fa
Timestamp: 1584633414 Timestamp [UCT]: 2020-03-19 15:56:54 Age [y:d:h:m:s]: 04:255:06:21:44
Block: 85198 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1078638 RingCT/type: yes/0
Extra: 01659c313a15e0d210e567c63ac4ecb216848f96b747adf23c77272739fe4e04fa02110000004fc2c2f844000000000000000000

1 output(s) for total of 320.408804074000 dcy

stealth address amount amount idx
00: c6daba3f853997c6634b179b9dcaa88e1aadf599ecdf11eaae5c02b3d843d41a 320.408804074000 154182 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": 85208, "vin": [ { "gen": { "height": 85198 } } ], "vout": [ { "amount": 320408804074, "target": { "key": "c6daba3f853997c6634b179b9dcaa88e1aadf599ecdf11eaae5c02b3d843d41a" } } ], "extra": [ 1, 101, 156, 49, 58, 21, 224, 210, 16, 229, 103, 198, 58, 196, 236, 178, 22, 132, 143, 150, 183, 71, 173, 242, 60, 119, 39, 39, 57, 254, 78, 4, 250, 2, 17, 0, 0, 0, 79, 194, 194, 248, 68, 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