Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83b9e217421c2bbeb9e328a30ac14cf3ceef1da8b417826df761eb5245291869

Tx prefix hash: c4335c3325c0c1acd96b1bae7e0c55151ac89c43e77f9d9c2037182561a86bc2
Tx public key: 714971c5f5f50e21907042ce2c86a94b9d42752fd03e2481ba1403c20df1b123
Timestamp: 1732980639 Timestamp [UCT]: 2024-11-30 15:30:39 Age [y:d:h:m:s]: 00:121:05:40:14
Block: 1165073 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86445 RingCT/type: yes/0
Extra: 01714971c5f5f50e21907042ce2c86a94b9d42752fd03e2481ba1403c20df1b123021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4f2b199317d3da2bdfd48512306b9ccca4ef8099e150ae772e2fd1a675144f1 0.600000000000 1650748 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": 1165083, "vin": [ { "gen": { "height": 1165073 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4f2b199317d3da2bdfd48512306b9ccca4ef8099e150ae772e2fd1a675144f1" } } ], "extra": [ 1, 113, 73, 113, 197, 245, 245, 14, 33, 144, 112, 66, 206, 44, 134, 169, 75, 157, 66, 117, 47, 208, 62, 36, 129, 186, 20, 3, 194, 13, 241, 177, 35, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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