Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7d58770031f0b17b85f10bf40896fda07c7eb5739ce01a9df0991443eb4a73e

Tx prefix hash: bd6a1d68640373e2d398e6e69722f78639e178f23a6e921be2917212368c9a8a
Tx public key: 0d5491b331d61336cd5bd4b3379de60c81e1aa3303354a27f2ef35825a339fa1
Timestamp: 1582848484 Timestamp [UCT]: 2020-02-28 00:08:04 Age [y:d:h:m:s]: 04:301:13:17:57
Block: 73203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1108981 RingCT/type: yes/0
Extra: 010d5491b331d61336cd5bd4b3379de60c81e1aa3303354a27f2ef35825a339fa102110000007c4ac5aa02000000000000000000

1 output(s) for total of 351.126727290000 dcy

stealth address amount amount idx
00: bda6d88e93829bf9dd6b23107906b90d5cf523f71ad2862d55873229579460c0 351.126727290000 135011 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": 73213, "vin": [ { "gen": { "height": 73203 } } ], "vout": [ { "amount": 351126727290, "target": { "key": "bda6d88e93829bf9dd6b23107906b90d5cf523f71ad2862d55873229579460c0" } } ], "extra": [ 1, 13, 84, 145, 179, 49, 214, 19, 54, 205, 91, 212, 179, 55, 157, 230, 12, 129, 225, 170, 51, 3, 53, 74, 39, 242, 239, 53, 130, 90, 51, 159, 161, 2, 17, 0, 0, 0, 124, 74, 197, 170, 2, 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