Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 044eb777f91a499528bab147d873c476fc82e67e8055d03d19f72824f5cc9326

Tx prefix hash: 79c2c8d16c91f44d02c9e137ccc3f0e80707b9a64f1362db0434bf8303c7a71c
Tx public key: 1bd91946a83a05c1a069238755baa940ba50f36114c8e8ffb69e8d9ab4114758
Timestamp: 1702369742 Timestamp [UCT]: 2023-12-12 08:29:02 Age [y:d:h:m:s]: 01:104:08:01:39
Block: 911401 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335686 RingCT/type: yes/0
Extra: 011bd91946a83a05c1a069238755baa940ba50f36114c8e8ffb69e8d9ab411475802110000000675e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4a6d60008f9d8da3daeef6b7a31252081e4a0775bdf98c50e3dda6c8dec6c32 0.600000000000 1368603 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": 911411, "vin": [ { "gen": { "height": 911401 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4a6d60008f9d8da3daeef6b7a31252081e4a0775bdf98c50e3dda6c8dec6c32" } } ], "extra": [ 1, 27, 217, 25, 70, 168, 58, 5, 193, 160, 105, 35, 135, 85, 186, 169, 64, 186, 80, 243, 97, 20, 200, 232, 255, 182, 158, 141, 154, 180, 17, 71, 88, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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