Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8970bfb09b410f4d23d1448b2ed990ae115c4ab4e69710cf9ea0444c5e4ad4a

Tx prefix hash: 7f7dbeace7d4790a655655da6487c74fdadf32c6ac8a8d059a79d0d26fc41fac
Tx public key: 56bb9e13e54ad1d5da1cb5541ed79ff2563b7728a7e69478b170cf61f35c6bcc
Timestamp: 1574182286 Timestamp [UCT]: 2019-11-19 16:51:26 Age [y:d:h:m:s]: 05:083:09:30:08
Block: 12674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1202533 RingCT/type: yes/0
Extra: 0156bb9e13e54ad1d5da1cb5541ed79ff2563b7728a7e69478b170cf61f35c6bcc021100000003ccefb800000000000000000000

1 output(s) for total of 557.194299124000 dcy

stealth address amount amount idx
00: f8d86d3bbabb0421c167715762092b51d5270544eff644c7ad528ec61114ea91 557.194299124000 14271 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": 12684, "vin": [ { "gen": { "height": 12674 } } ], "vout": [ { "amount": 557194299124, "target": { "key": "f8d86d3bbabb0421c167715762092b51d5270544eff644c7ad528ec61114ea91" } } ], "extra": [ 1, 86, 187, 158, 19, 229, 74, 209, 213, 218, 28, 181, 84, 30, 215, 159, 242, 86, 59, 119, 40, 167, 230, 148, 120, 177, 112, 207, 97, 243, 92, 107, 204, 2, 17, 0, 0, 0, 3, 204, 239, 184, 0, 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