Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89e8504c7ed257b5de8e0cb27c91aa28af9231e311bdf0e84126275ab0c55890

Tx prefix hash: 64f87d67076d57b3445649d110d96279f1e32b45a7195bd3e8b0ea7e43b11c48
Tx public key: 7f828bf31a4c121a68b96c122fd813c3e786b82e85f6a29da53c2658427b40b0
Timestamp: 1649637438 Timestamp [UCT]: 2022-04-11 00:37:18 Age [y:d:h:m:s]: 02:280:02:27:11
Block: 477622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 719983 RingCT/type: yes/0
Extra: 017f828bf31a4c121a68b96c122fd813c3e786b82e85f6a29da53c2658427b40b0021100000011c9067537000000000000000000

1 output(s) for total of 16.048715637000 dcy

stealth address amount amount idx
00: 40442f3750fa4f87ebf716e4710c1fabe24ab217ad14984989c7392f8018c4e4 16.048715637000 898297 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": 477632, "vin": [ { "gen": { "height": 477622 } } ], "vout": [ { "amount": 16048715637, "target": { "key": "40442f3750fa4f87ebf716e4710c1fabe24ab217ad14984989c7392f8018c4e4" } } ], "extra": [ 1, 127, 130, 139, 243, 26, 76, 18, 26, 104, 185, 108, 18, 47, 216, 19, 195, 231, 134, 184, 46, 133, 246, 162, 157, 165, 60, 38, 88, 66, 123, 64, 176, 2, 17, 0, 0, 0, 17, 201, 6, 117, 55, 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