Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73b62bddccfa9ffc814c64c6c66c620d3760b49d157e925d25b40e97882c4d5d

Tx prefix hash: 11a0ec04b942b790e5e145a5a8ac1d0a4ac9e852506ecd675592ec504db9ae56
Tx public key: e8281cdb7ed51268b2b5ff8591801bb649bf29649a9dc011a100ade212780fb2
Timestamp: 1711742457 Timestamp [UCT]: 2024-03-29 20:00:57 Age [y:d:h:m:s]: 01:085:10:46:25
Block: 989118 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321853 RingCT/type: yes/0
Extra: 01e8281cdb7ed51268b2b5ff8591801bb649bf29649a9dc011a100ade212780fb20211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55cb7ca3eb41a8a40dbe4fea72ffd6e52f69252dce088153ed731a282a1df6e2 0.600000000000 1449413 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": 989128, "vin": [ { "gen": { "height": 989118 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55cb7ca3eb41a8a40dbe4fea72ffd6e52f69252dce088153ed731a282a1df6e2" } } ], "extra": [ 1, 232, 40, 28, 219, 126, 213, 18, 104, 178, 181, 255, 133, 145, 128, 27, 182, 73, 191, 41, 100, 154, 157, 192, 17, 161, 0, 173, 226, 18, 120, 15, 178, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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