Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62d6af48008bc1369642fd41427a04d64230d9476c7cbfb3d77631c5afc0326a

Tx prefix hash: 26e21ad66779a392397bf2a898a26a560f4f6853c048699478dfc669efc140e6
Tx public key: d862de260d3b8d0e523d17a7a053a63bf88680339ef64a801b4c7c6d59b7a489
Timestamp: 1703743695 Timestamp [UCT]: 2023-12-28 06:08:15 Age [y:d:h:m:s]: 01:120:14:50:59
Block: 922783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347333 RingCT/type: yes/0
Extra: 01d862de260d3b8d0e523d17a7a053a63bf88680339ef64a801b4c7c6d59b7a4890211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7bed5410b93060840e5a088d0c3c5d91ce431df5f42e2ee9f502722b3707573c 0.600000000000 1380487 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": 922793, "vin": [ { "gen": { "height": 922783 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7bed5410b93060840e5a088d0c3c5d91ce431df5f42e2ee9f502722b3707573c" } } ], "extra": [ 1, 216, 98, 222, 38, 13, 59, 141, 14, 82, 61, 23, 167, 160, 83, 166, 59, 248, 134, 128, 51, 158, 246, 74, 128, 27, 76, 124, 109, 89, 183, 164, 137, 2, 17, 0, 0, 0, 5, 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