Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e4bde6fbd19bfeee3c7efc75a910fce7ce55a6d8751ee95e6029af0f56671a0

Tx prefix hash: 16571b5993f7835968c45ea889c40db611690224d62f839146fc06e4f05fd2c6
Tx public key: dc5a61c9e030b571fa39a05bc01103408799a9c4065be6d47e2c16ec11374d4b
Timestamp: 1732631930 Timestamp [UCT]: 2024-11-26 14:38:50 Age [y:d:h:m:s]: 00:135:07:48:03
Block: 1162181 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96532 RingCT/type: yes/0
Extra: 01dc5a61c9e030b571fa39a05bc01103408799a9c4065be6d47e2c16ec11374d4b021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 179aa33a9af3daac5e29183348fa8ba3ed0b56263ae566fb033e63f2c76aa14e 0.600000000000 1647836 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": 1162191, "vin": [ { "gen": { "height": 1162181 } } ], "vout": [ { "amount": 600000000, "target": { "key": "179aa33a9af3daac5e29183348fa8ba3ed0b56263ae566fb033e63f2c76aa14e" } } ], "extra": [ 1, 220, 90, 97, 201, 224, 48, 181, 113, 250, 57, 160, 91, 192, 17, 3, 64, 135, 153, 169, 196, 6, 91, 230, 212, 126, 44, 22, 236, 17, 55, 77, 75, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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