Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e677a3c30cb9f23ec3bd13a81e266e0fe6de0066ea3fb328015c707bf94ab53d

Tx prefix hash: 137e209798a9e4a2001d85df8092af35d984c5fe2ced435dbf17fa9042bfd06b
Tx public key: 301ca1b3a2ab08fe8ce8bffe5ad62c4fdda0170a3754651763e5443d1d3dab25
Timestamp: 1700828895 Timestamp [UCT]: 2023-11-24 12:28:15 Age [y:d:h:m:s]: 01:196:12:12:24
Block: 898609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401662 RingCT/type: yes/0
Extra: 01301ca1b3a2ab08fe8ce8bffe5ad62c4fdda0170a3754651763e5443d1d3dab25021100000004faf35c9c000000000000000000

1 output(s) for total of 0.646450593000 dcy

stealth address amount amount idx
00: 3f5e2ecf3ae1b5f04835b784f4bcfb91f4fd2446326cf5998085c81bbeb42ef1 0.646450593000 1355032 of 0

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": 898619, "vin": [ { "gen": { "height": 898609 } } ], "vout": [ { "amount": 646450593, "target": { "key": "3f5e2ecf3ae1b5f04835b784f4bcfb91f4fd2446326cf5998085c81bbeb42ef1" } } ], "extra": [ 1, 48, 28, 161, 179, 162, 171, 8, 254, 140, 232, 191, 254, 90, 214, 44, 79, 221, 160, 23, 10, 55, 84, 101, 23, 99, 229, 68, 61, 29, 61, 171, 37, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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