Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ddc2863182dc428f104c696097493fc3cff98c7eae8fc6d8b1903cb9624d8c3

Tx prefix hash: ed7e9178473bd3d46363763b8763cf46da83861f75f0fb6f36e46d484138c98c
Tx public key: 1d21136d01d46abd7850b19705fb66418ea7d75ff65ecf02aa66b943a5f075e2
Timestamp: 1704008870 Timestamp [UCT]: 2023-12-31 07:47:50 Age [y:d:h:m:s]: 01:054:02:28:31
Block: 924971 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299742 RingCT/type: yes/0
Extra: 011d21136d01d46abd7850b19705fb66418ea7d75ff65ecf02aa66b943a5f075e202110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5268ba9159b9cbbaf9f682fbc5d7db0e02a1ec5ae20c407d8e1f95cf3dc6030 0.600000000000 1382731 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": 924981, "vin": [ { "gen": { "height": 924971 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5268ba9159b9cbbaf9f682fbc5d7db0e02a1ec5ae20c407d8e1f95cf3dc6030" } } ], "extra": [ 1, 29, 33, 19, 109, 1, 212, 106, 189, 120, 80, 177, 151, 5, 251, 102, 65, 142, 167, 215, 95, 246, 94, 207, 2, 170, 102, 185, 67, 165, 240, 117, 226, 2, 17, 0, 0, 0, 5, 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