Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0dc0615598da26f0dab43726306310c686f8e820fca60814b34ac727da2c92dd

Tx prefix hash: 33a2b52eddb4a91750f2f9f0a302b746b5f9b5077de3cd7b83516ddb0acbb2ff
Tx public key: 6c191507b864eff541762c8c1c60da7d5ee0b11dc59921b1a79d0d84d898e798
Timestamp: 1588732699 Timestamp [UCT]: 2020-05-06 02:38:19 Age [y:d:h:m:s]: 04:313:09:41:29
Block: 98562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1140560 RingCT/type: yes/0
Extra: 016c191507b864eff541762c8c1c60da7d5ee0b11dc59921b1a79d0d84d898e798021100000033a86a1a65000000000000000000

1 output(s) for total of 289.366673999000 dcy

stealth address amount amount idx
00: b7cd42cf1e982e5f3dcaa5b889dbedda4e2ee6cabe917cf70d3f154a3b5189cb 289.366673999000 174236 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": 98572, "vin": [ { "gen": { "height": 98562 } } ], "vout": [ { "amount": 289366673999, "target": { "key": "b7cd42cf1e982e5f3dcaa5b889dbedda4e2ee6cabe917cf70d3f154a3b5189cb" } } ], "extra": [ 1, 108, 25, 21, 7, 184, 100, 239, 245, 65, 118, 44, 140, 28, 96, 218, 125, 94, 224, 177, 29, 197, 153, 33, 177, 167, 157, 13, 132, 216, 152, 231, 152, 2, 17, 0, 0, 0, 51, 168, 106, 26, 101, 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