Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1394a71b534005ab4d96a7950d11dad4687ca5d95669762044d867993ec8f6b8

Tx prefix hash: d300ec752a530e92b6a8f5e0392b55fd32ab57d789dc05a86edd241750ca1207
Tx public key: 25b9239639d534a331c82c8c54490d53a51f22de4a3d3013c6aed07d883e88cb
Timestamp: 1730175587 Timestamp [UCT]: 2024-10-29 04:19:47 Age [y:d:h:m:s]: 00:143:13:41:42
Block: 1141866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102415 RingCT/type: yes/0
Extra: 0125b9239639d534a331c82c8c54490d53a51f22de4a3d3013c6aed07d883e88cb0211000000013cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a7f586c7f3117f2991c34e747b3ae6aa6a1958b615fe92ab1d1d9d12428c36e 0.600000000000 1625697 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": 1141876, "vin": [ { "gen": { "height": 1141866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a7f586c7f3117f2991c34e747b3ae6aa6a1958b615fe92ab1d1d9d12428c36e" } } ], "extra": [ 1, 37, 185, 35, 150, 57, 213, 52, 163, 49, 200, 44, 140, 84, 73, 13, 83, 165, 31, 34, 222, 74, 61, 48, 19, 198, 174, 208, 125, 136, 62, 136, 203, 2, 17, 0, 0, 0, 1, 60, 208, 252, 6, 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