Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92180f5902bafc1cd2b1e461ea334e4d32bdaeede26cb7cacce7d10886e38119

Tx prefix hash: d4b2e75a5288ca4895ea292e8c2f962c30a551e5df0c9ac97d5caac1c4fcf90c
Tx public key: 64d3fa0da8cf3529f283bf9018194896acd618037d716186c7934aa30b6de4d7
Timestamp: 1718007978 Timestamp [UCT]: 2024-06-10 08:26:18 Age [y:d:h:m:s]: 00:296:14:04:24
Block: 1041041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211942 RingCT/type: yes/0
Extra: 0164d3fa0da8cf3529f283bf9018194896acd618037d716186c7934aa30b6de4d70211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb8d7f524170e4b3a29b675d5e095d774bb18dd9f0a866e3d4cbe81f8875768d 0.600000000000 1509706 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": 1041051, "vin": [ { "gen": { "height": 1041041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb8d7f524170e4b3a29b675d5e095d774bb18dd9f0a866e3d4cbe81f8875768d" } } ], "extra": [ 1, 100, 211, 250, 13, 168, 207, 53, 41, 242, 131, 191, 144, 24, 25, 72, 150, 172, 214, 24, 3, 125, 113, 97, 134, 199, 147, 74, 163, 11, 109, 228, 215, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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