Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5415adda6f314ba823f0f2900a71ab8a3c2beffd0dad2dd34c35b7b56479b60a

Tx prefix hash: 9aaf69e90dcd0167849b25167e5e3d2cc144c15233bcf7ca71f5dfe1427cc7db
Tx public key: 642bd48c19c504b193ec73d1fa250cf1a6b0f5f7e12f853c9f476565758b1902
Timestamp: 1725273633 Timestamp [UCT]: 2024-09-02 10:40:33 Age [y:d:h:m:s]: 00:219:21:40:52
Block: 1101277 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157013 RingCT/type: yes/0
Extra: 01642bd48c19c504b193ec73d1fa250cf1a6b0f5f7e12f853c9f476565758b1902021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0147359a4567132faccb0e6d12b482f5313930a2bc721d57fd636f756ee6c91 0.600000000000 1577264 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": 1101287, "vin": [ { "gen": { "height": 1101277 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0147359a4567132faccb0e6d12b482f5313930a2bc721d57fd636f756ee6c91" } } ], "extra": [ 1, 100, 43, 212, 140, 25, 197, 4, 177, 147, 236, 115, 209, 250, 37, 12, 241, 166, 176, 245, 247, 225, 47, 133, 60, 159, 71, 101, 101, 117, 139, 25, 2, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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