Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb944c8d7827c55f42ccc59687a7b3e275e5f429d4c77acbd12f230c2761688b

Tx prefix hash: fa03dead98012cbda2268807044ed053d6c491d47d5ab3a16a717906f203391d
Tx public key: aee6ecddc387cad8d66252bc02bd6df50e9bc5385a9ea6ab0a14b002c854d0e4
Timestamp: 1702239025 Timestamp [UCT]: 2023-12-10 20:10:25 Age [y:d:h:m:s]: 01:166:15:01:27
Block: 910311 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380264 RingCT/type: yes/0
Extra: 01aee6ecddc387cad8d66252bc02bd6df50e9bc5385a9ea6ab0a14b002c854d0e402110000000433af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f354d95bfbd9d74f8c18d3bcdcb7dc66be0fadf0caa06bcda0b6ae0f627eb48 0.600000000000 1367460 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": 910321, "vin": [ { "gen": { "height": 910311 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f354d95bfbd9d74f8c18d3bcdcb7dc66be0fadf0caa06bcda0b6ae0f627eb48" } } ], "extra": [ 1, 174, 230, 236, 221, 195, 135, 202, 216, 214, 98, 82, 188, 2, 189, 109, 245, 14, 155, 197, 56, 90, 158, 166, 171, 10, 20, 176, 2, 200, 84, 208, 228, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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