Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89c4faf21495757ce33261b1050765fcd15035dcc36ad5a3e0852c50c87b632e

Tx prefix hash: ae3311847ebd5c2cfa8341653e693963f7c6f2144399bc7c7e25f20b79beac86
Tx public key: ae0b74aa21910a1c6fd2a98c55e75a8165920ca285fe7bbb2b1713c26f25da5b
Timestamp: 1678107699 Timestamp [UCT]: 2023-03-06 13:01:39 Age [y:d:h:m:s]: 01:313:22:36:04
Block: 711143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485288 RingCT/type: yes/0
Extra: 01ae0b74aa21910a1c6fd2a98c55e75a8165920ca285fe7bbb2b1713c26f25da5b0211000000068b7b6602000000000000000000

1 output(s) for total of 2.702016075000 dcy

stealth address amount amount idx
00: 608d7611241a6ee0d06b116adb191892259609777cd7008b0c9b4a49204747b6 2.702016075000 1155258 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": 711153, "vin": [ { "gen": { "height": 711143 } } ], "vout": [ { "amount": 2702016075, "target": { "key": "608d7611241a6ee0d06b116adb191892259609777cd7008b0c9b4a49204747b6" } } ], "extra": [ 1, 174, 11, 116, 170, 33, 145, 10, 28, 111, 210, 169, 140, 85, 231, 90, 129, 101, 146, 12, 162, 133, 254, 123, 187, 43, 23, 19, 194, 111, 37, 218, 91, 2, 17, 0, 0, 0, 6, 139, 123, 102, 2, 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