Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4d8f86a78d44740c6c64cfcf07874f25fbf0bc20eab442b9f948daed3c45fef

Tx prefix hash: b0c5b09a4ba6f13bea56bb62d64376f1036caa041aa5a6ed00ca920b54c51c4d
Tx public key: d893697d7357905605036e7d06da67ff45e814b44f286bb85c27a5b37ee13600
Timestamp: 1721180866 Timestamp [UCT]: 2024-07-17 01:47:46 Age [y:d:h:m:s]: 00:131:00:43:36
Block: 1067361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93742 RingCT/type: yes/0
Extra: 01d893697d7357905605036e7d06da67ff45e814b44f286bb85c27a5b37ee1360002110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5851de6f5fd0e3b2376385d9e81f92fab5cb2e5e5ceb571ba2255616ecee8c9b 0.600000000000 1538150 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": 1067371, "vin": [ { "gen": { "height": 1067361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5851de6f5fd0e3b2376385d9e81f92fab5cb2e5e5ceb571ba2255616ecee8c9b" } } ], "extra": [ 1, 216, 147, 105, 125, 115, 87, 144, 86, 5, 3, 110, 125, 6, 218, 103, 255, 69, 232, 20, 180, 79, 40, 107, 184, 92, 39, 165, 179, 126, 225, 54, 0, 2, 17, 0, 0, 0, 10, 145, 225, 60, 4, 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