Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ad247d3419a29548f4fe008d188dd2e46ba33f006a74cbfc2b67cf59d1e9e73

Tx prefix hash: 1fc8181a5cc00b391386da72d4158c1b28ae230ab40fb7687ee2c5d6af8623dd
Tx public key: 5413b7d04b4a6a8a776953ad8d94cfdb72a2cdecaea4cd7e4894ec1bc575faa2
Timestamp: 1639126095 Timestamp [UCT]: 2021-12-10 08:48:15 Age [y:d:h:m:s]: 03:021:13:12:03
Block: 392377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 794341 RingCT/type: yes/0
Extra: 015413b7d04b4a6a8a776953ad8d94cfdb72a2cdecaea4cd7e4894ec1bc575faa2021100000002d6e4826b000000000000000000

1 output(s) for total of 30.753353345000 dcy

stealth address amount amount idx
00: e3c0efc4b3733e8e979b87757c049fdca104f71e443314f3f5eb02dfb9b0a1d1 30.753353345000 789220 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": 392387, "vin": [ { "gen": { "height": 392377 } } ], "vout": [ { "amount": 30753353345, "target": { "key": "e3c0efc4b3733e8e979b87757c049fdca104f71e443314f3f5eb02dfb9b0a1d1" } } ], "extra": [ 1, 84, 19, 183, 208, 75, 74, 106, 138, 119, 105, 83, 173, 141, 148, 207, 219, 114, 162, 205, 236, 174, 164, 205, 126, 72, 148, 236, 27, 197, 117, 250, 162, 2, 17, 0, 0, 0, 2, 214, 228, 130, 107, 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