Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a4203079f4008924dc17d3c0de5a0930f79010df627248f9771d214a3d1b384

Tx prefix hash: 993fe3f23e2a7f2c3b3a78ee7f1a42f0a4e2e171228ffaa815368c6e82e26076
Tx public key: 708d9bf5488593f71e1f934a92be7bb60808e8d6fd27f65d383592db003e1b03
Timestamp: 1705875069 Timestamp [UCT]: 2024-01-21 22:11:09 Age [y:d:h:m:s]: 00:307:17:30:37
Block: 940420 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220372 RingCT/type: yes/0
Extra: 01708d9bf5488593f71e1f934a92be7bb60808e8d6fd27f65d383592db003e1b0302110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7bc15612f18391e81e45490ff0a142825e470cc39fcd64ef64b39f6b7349c6cf 0.600000000000 1398556 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": 940430, "vin": [ { "gen": { "height": 940420 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7bc15612f18391e81e45490ff0a142825e470cc39fcd64ef64b39f6b7349c6cf" } } ], "extra": [ 1, 112, 141, 155, 245, 72, 133, 147, 247, 30, 31, 147, 74, 146, 190, 123, 182, 8, 8, 232, 214, 253, 39, 246, 93, 56, 53, 146, 219, 0, 62, 27, 3, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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