Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16402c06a0e44ec772466043cbb1fb37583d66e5dd71d5290afac45acd90efc5

Tx prefix hash: b221eb6903d56acb09881ddb82195b06135fd1751b0b09a2e07984b76672a491
Tx public key: 96558d22442fb499e68cb1b4d37f2976b9594ae5e5a40211a0e4dd71e6fd7fdd
Timestamp: 1700258900 Timestamp [UCT]: 2023-11-17 22:08:20 Age [y:d:h:m:s]: 02:005:18:15:09
Block: 893893 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 523883 RingCT/type: yes/0
Extra: 0196558d22442fb499e68cb1b4d37f2976b9594ae5e5a40211a0e4dd71e6fd7fdd021100000002faf35c9c000000000000000000

1 output(s) for total of 0.670133626000 dcy

stealth address amount amount idx
00: 1fbd4ab919a0c1aa9f3c27dd5d6fc1c465bbe1d4da284fecb48d19f8b3fd1e74 0.670133626000 1350078 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": 893903, "vin": [ { "gen": { "height": 893893 } } ], "vout": [ { "amount": 670133626, "target": { "key": "1fbd4ab919a0c1aa9f3c27dd5d6fc1c465bbe1d4da284fecb48d19f8b3fd1e74" } } ], "extra": [ 1, 150, 85, 141, 34, 68, 47, 180, 153, 230, 140, 177, 180, 211, 127, 41, 118, 185, 89, 74, 229, 229, 164, 2, 17, 160, 228, 221, 113, 230, 253, 127, 221, 2, 17, 0, 0, 0, 2, 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