Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e677a99c1ef55a7f44fbcbda1fa86af3deae7a32b2de875662907905c9253e5

Tx prefix hash: bcf24b4d2f1e26dea4e0977b4f250b66013dcbd8f962a48eecea1704d6cc23c7
Tx public key: 2ba0038108b7682f92520ea7f2c0bb84a0cad8e5a85709d4fe7eb61f216b78a2
Timestamp: 1707076821 Timestamp [UCT]: 2024-02-04 20:00:21 Age [y:d:h:m:s]: 01:334:09:43:35
Block: 950406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497863 RingCT/type: yes/0
Extra: 012ba0038108b7682f92520ea7f2c0bb84a0cad8e5a85709d4fe7eb61f216b78a202110000000210a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d6959bd3b7ce10036fefd063fbf24777201f4da9fbcbbeff238c73c31e26218 0.600000000000 1409022 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": 950416, "vin": [ { "gen": { "height": 950406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d6959bd3b7ce10036fefd063fbf24777201f4da9fbcbbeff238c73c31e26218" } } ], "extra": [ 1, 43, 160, 3, 129, 8, 183, 104, 47, 146, 82, 14, 167, 242, 192, 187, 132, 160, 202, 216, 229, 168, 87, 9, 212, 254, 126, 182, 31, 33, 107, 120, 162, 2, 17, 0, 0, 0, 2, 16, 161, 116, 143, 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