Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c226d20aba602d36397ef6f60ab0e01ac417c37d569e6feee0c18f3c9b3cf4c6

Tx prefix hash: 5dc23311beb19c87f4776b1886407e255fa6048d8cc988bc8169a5fb6eff300d
Tx public key: 77fd901eaf7582c287b4ab64f31c6bd9acbc9e63fcfb4e2bfe8c24697bf129c4
Timestamp: 1737335155 Timestamp [UCT]: 2025-01-20 01:05:55 Age [y:d:h:m:s]: 00:336:07:27:11
Block: 1201076 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237953 RingCT/type: yes/0
Extra: 0177fd901eaf7582c287b4ab64f31c6bd9acbc9e63fcfb4e2bfe8c24697bf129c40211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ab223cae6ff18f2386e194d92463e2ae81b71bb56cb24799fdeaa7140d135ed 0.600000000000 1687725 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": 1201086, "vin": [ { "gen": { "height": 1201076 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ab223cae6ff18f2386e194d92463e2ae81b71bb56cb24799fdeaa7140d135ed" } } ], "extra": [ 1, 119, 253, 144, 30, 175, 117, 130, 194, 135, 180, 171, 100, 243, 28, 107, 217, 172, 188, 158, 99, 252, 251, 78, 43, 254, 140, 36, 105, 123, 241, 41, 196, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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