Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1a95471d59c47266d2e25e1283ca835d31f5bd96058874b1c6cfbf4d5756063

Tx prefix hash: 326dda93184f3c8bb67631fe92caa7b380d027c53cff0958e823d2b022a352f3
Tx public key: c17070e1b1d550ceb5d9be7718cad9b7b949471ee7d8adc59fdcec91d50a515a
Timestamp: 1747246145 Timestamp [UCT]: 2025-05-14 18:09:05 Age [y:d:h:m:s]: 00:146:06:44:51
Block: 1282918 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102176 RingCT/type: yes/0
Extra: 01c17070e1b1d550ceb5d9be7718cad9b7b949471ee7d8adc59fdcec91d50a515a0211000000059f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cc2c65ac51858376780f59a501373db896bfe913c8a1e650839b1f4c8a537bf 0.600000000000 1770333 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": 1282928, "vin": [ { "gen": { "height": 1282918 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cc2c65ac51858376780f59a501373db896bfe913c8a1e650839b1f4c8a537bf" } } ], "extra": [ 1, 193, 112, 112, 225, 177, 213, 80, 206, 181, 217, 190, 119, 24, 202, 217, 183, 185, 73, 71, 30, 231, 216, 173, 197, 159, 220, 236, 145, 213, 10, 81, 90, 2, 17, 0, 0, 0, 5, 159, 159, 230, 140, 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