Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ad5c98c16c888535e32a2c1d714f98b34bce2368b70126997dd1ae30f465682

Tx prefix hash: 032eb2389700867743116fdb04e7301a958d417b68e102baf1cea3ff65fb9b8b
Tx public key: 177427a506707710fa4df63e1a5fe83e0261ca2140c9b532d9fe95ec89c804a5
Timestamp: 1716138167 Timestamp [UCT]: 2024-05-19 17:02:47 Age [y:d:h:m:s]: 00:285:23:17:40
Block: 1025539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204380 RingCT/type: yes/0
Extra: 01177427a506707710fa4df63e1a5fe83e0261ca2140c9b532d9fe95ec89c804a502110000000f59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7006b9d793c8480a0cb5ba328846dc54c0f0eaab56a4405a66dc9701502b0c41 0.600000000000 1492118 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": 1025549, "vin": [ { "gen": { "height": 1025539 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7006b9d793c8480a0cb5ba328846dc54c0f0eaab56a4405a66dc9701502b0c41" } } ], "extra": [ 1, 23, 116, 39, 165, 6, 112, 119, 16, 250, 77, 246, 62, 26, 95, 232, 62, 2, 97, 202, 33, 64, 201, 181, 50, 217, 254, 149, 236, 137, 200, 4, 165, 2, 17, 0, 0, 0, 15, 89, 218, 211, 245, 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