Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35d5f0226bda857cc5caf7e9e52ebfb82a5969ff8a64a4c6cba657d812315c6a

Tx prefix hash: 34b26f3e37f8176aa5893aed290106ae02f28e1c3047e4fe6d73ed52ccee1bb4
Tx public key: 1fd4fa887c615be53b9601c24e98f71505f5c3ba4a1b9b85cfaf2712697e270d
Timestamp: 1581951110 Timestamp [UCT]: 2020-02-17 14:51:50 Age [y:d:h:m:s]: 04:324:22:31:46
Block: 66930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1124560 RingCT/type: yes/0
Extra: 011fd4fa887c615be53b9601c24e98f71505f5c3ba4a1b9b85cfaf2712697e270d021100000004c71d3ff9000000000000000000

1 output(s) for total of 368.343800993000 dcy

stealth address amount amount idx
00: 2d36afb92a128be3d89436f5b7595ee345dc4b025a1481d86f45d7ecfd74afe5 368.343800993000 123189 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": 66940, "vin": [ { "gen": { "height": 66930 } } ], "vout": [ { "amount": 368343800993, "target": { "key": "2d36afb92a128be3d89436f5b7595ee345dc4b025a1481d86f45d7ecfd74afe5" } } ], "extra": [ 1, 31, 212, 250, 136, 124, 97, 91, 229, 59, 150, 1, 194, 78, 152, 247, 21, 5, 245, 195, 186, 74, 27, 155, 133, 207, 175, 39, 18, 105, 126, 39, 13, 2, 17, 0, 0, 0, 4, 199, 29, 63, 249, 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