Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd5a493185d4afc3c0e0cb7b746fd2716d5b3066d6ca6f1f3012d566431e8335

Tx prefix hash: 22008429fab0911d2a20cfe2989e6edb8eaff1b84cf74c548f979afa15d738da
Tx public key: 5231d1a8fa9ae38df5da2a1becb4fc55e82c8f24a9276db69665719abe57c38e
Timestamp: 1710646531 Timestamp [UCT]: 2024-03-17 03:35:31 Age [y:d:h:m:s]: 01:029:02:18:43
Block: 980029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281765 RingCT/type: yes/0
Extra: 015231d1a8fa9ae38df5da2a1becb4fc55e82c8f24a9276db69665719abe57c38e0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e047ace16a304bb69482665a74531c46b8984a6038060c08b493d78b3a85069 0.600000000000 1440088 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": 980039, "vin": [ { "gen": { "height": 980029 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e047ace16a304bb69482665a74531c46b8984a6038060c08b493d78b3a85069" } } ], "extra": [ 1, 82, 49, 209, 168, 250, 154, 227, 141, 245, 218, 42, 27, 236, 180, 252, 85, 232, 44, 143, 36, 169, 39, 109, 182, 150, 101, 113, 154, 190, 87, 195, 142, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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