Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd5bcfbf04bfc8fc6827982411029df012fdd2cd4c2345c2497fa2c57716d077

Tx prefix hash: 77282cc16babcb178d2048e9c7a1b5d3c7d42e56c9706f992bf8281a52b1624f
Tx public key: a783ffd56a70a6c1ea131b6f618a939d8eab17f185ce9d1c9b0e3b85319855de
Timestamp: 1583537117 Timestamp [UCT]: 2020-03-06 23:25:17 Age [y:d:h:m:s]: 04:336:01:28:37
Block: 77786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1134501 RingCT/type: yes/0
Extra: 01a783ffd56a70a6c1ea131b6f618a939d8eab17f185ce9d1c9b0e3b85319855de02110000000427105131000000000000000000

1 output(s) for total of 339.049793876000 dcy

stealth address amount amount idx
00: 09ce8e0e702b417f210cc498d0766dd67d94908e66c9776073e0dfbee3f2c1a6 339.049793876000 142987 of 0

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": 77796, "vin": [ { "gen": { "height": 77786 } } ], "vout": [ { "amount": 339049793876, "target": { "key": "09ce8e0e702b417f210cc498d0766dd67d94908e66c9776073e0dfbee3f2c1a6" } } ], "extra": [ 1, 167, 131, 255, 213, 106, 112, 166, 193, 234, 19, 27, 111, 97, 138, 147, 157, 142, 171, 23, 241, 133, 206, 157, 28, 155, 14, 59, 133, 49, 152, 85, 222, 2, 17, 0, 0, 0, 4, 39, 16, 81, 49, 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