Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09765685e041c426cc2390cb78067d8c51e39751f6cae68f825836a26853c83f

Tx prefix hash: ea5ec9aeec685190c61cad59e6120ecd66e09fefffe00b50a3e4dbf4cd64c20a
Tx public key: 6da5fb7cf1ab42ad0e401ab3ec4bee4d9e8d975d8ec1b3c02ec877bd2427cf04
Timestamp: 1706239335 Timestamp [UCT]: 2024-01-26 03:22:15 Age [y:d:h:m:s]: 01:067:19:48:08
Block: 943441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309560 RingCT/type: yes/0
Extra: 016da5fb7cf1ab42ad0e401ab3ec4bee4d9e8d975d8ec1b3c02ec877bd2427cf0402110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bad945f473241a519759bfdf6b15c8faba6fbf7568c17a44094ec16f40504244 0.600000000000 1401647 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": 943451, "vin": [ { "gen": { "height": 943441 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bad945f473241a519759bfdf6b15c8faba6fbf7568c17a44094ec16f40504244" } } ], "extra": [ 1, 109, 165, 251, 124, 241, 171, 66, 173, 14, 64, 26, 179, 236, 75, 238, 77, 158, 141, 151, 93, 142, 193, 179, 192, 46, 200, 119, 189, 36, 39, 207, 4, 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