Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86c06c6635fb404c5d3f61f0d3b27491e2575109862db9ef3f27591e42508cdf

Tx prefix hash: a6ffb2e1b3cbef99d685aff9dd7928b9c545bf443cf40bd71a478ae0807b2666
Tx public key: 856066d4510652a2edd07b1f2208efe6e2b5777bd2eb832a796f81d929bf015b
Timestamp: 1751239783 Timestamp [UCT]: 2025-06-29 23:29:43 Age [y:d:h:m:s]: 00:143:08:31:46
Block: 1315472 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100633 RingCT/type: yes/0
Extra: 01856066d4510652a2edd07b1f2208efe6e2b5777bd2eb832a796f81d929bf015b02110000000701491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6515f746b1981a5e538f202ef684d9a9f0857c9d9e47b0161d200b2e9bf0476e 0.600000000000 1803127 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": 1315482, "vin": [ { "gen": { "height": 1315472 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6515f746b1981a5e538f202ef684d9a9f0857c9d9e47b0161d200b2e9bf0476e" } } ], "extra": [ 1, 133, 96, 102, 212, 81, 6, 82, 162, 237, 208, 123, 31, 34, 8, 239, 230, 226, 181, 119, 123, 210, 235, 131, 42, 121, 111, 129, 217, 41, 191, 1, 91, 2, 17, 0, 0, 0, 7, 1, 73, 31, 136, 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