Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c8d26f1db64c898d987f31cdbed625a3897a36e0b0860c856553bea738abfac

Tx prefix hash: 4eac0719ced921e3f97cb805d5dc892698b74005064b228788b96bbe39cf7e6e
Tx public key: d850c5a8efc7cb8096175d149a7936236ba93009e0081ba423c2b3a54eb4d1dc
Timestamp: 1729378553 Timestamp [UCT]: 2024-10-19 22:55:53 Age [y:d:h:m:s]: 00:170:20:58:56
Block: 1135298 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121902 RingCT/type: yes/0
Extra: 01d850c5a8efc7cb8096175d149a7936236ba93009e0081ba423c2b3a54eb4d1dc021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 174497dde61e631bbf1dc70a8ea9adb56e1c3481e2c49fd9c62aa1844f01b946 0.600000000000 1618635 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": 1135308, "vin": [ { "gen": { "height": 1135298 } } ], "vout": [ { "amount": 600000000, "target": { "key": "174497dde61e631bbf1dc70a8ea9adb56e1c3481e2c49fd9c62aa1844f01b946" } } ], "extra": [ 1, 216, 80, 197, 168, 239, 199, 203, 128, 150, 23, 93, 20, 154, 121, 54, 35, 107, 169, 48, 9, 224, 8, 27, 164, 35, 194, 179, 165, 78, 180, 209, 220, 2, 17, 0, 0, 0, 1, 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