Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f952db2c0903c936ebbd5da5221d3d298e5108d3a151b13cbc884395a65c5d4a

Tx prefix hash: 7b0f38f44ca31620eb37b1a16f8085603c815b5b696cff5597e384d537cb730f
Tx public key: 824b6458bafc7f2cf78b96abf742cb55cd8a3b6ff8d82ed8ef988b22d71812d2
Timestamp: 1728275033 Timestamp [UCT]: 2024-10-07 04:23:53 Age [y:d:h:m:s]: 00:248:22:53:41
Block: 1126162 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177722 RingCT/type: yes/0
Extra: 01824b6458bafc7f2cf78b96abf742cb55cd8a3b6ff8d82ed8ef988b22d71812d202110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fa0e7752fde70c6bd95013371635c1a549aa8d826d19d086aead931292cc5e5 0.600000000000 1608951 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": 1126172, "vin": [ { "gen": { "height": 1126162 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fa0e7752fde70c6bd95013371635c1a549aa8d826d19d086aead931292cc5e5" } } ], "extra": [ 1, 130, 75, 100, 88, 186, 252, 127, 44, 247, 139, 150, 171, 247, 66, 203, 85, 205, 138, 59, 111, 248, 216, 46, 216, 239, 152, 139, 34, 215, 24, 18, 210, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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