Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a02a0ec777c703f35c044917788a7c2eca53c403a80826a4d1fc4109b693b07d

Tx prefix hash: 15e23110027c69f68df699cc74ad3e182cafcc2fd505eeb4bdc37635ad8e7c07
Tx public key: c4e16d9a38b906f5ec88fc4828b5d3244e5649b1f72cacfbb3b0aa679109e190
Timestamp: 1718649533 Timestamp [UCT]: 2024-06-17 18:38:53 Age [y:d:h:m:s]: 00:358:02:23:57
Block: 1046364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255942 RingCT/type: yes/0
Extra: 01c4e16d9a38b906f5ec88fc4828b5d3244e5649b1f72cacfbb3b0aa679109e19002110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e78037a5410b966e4486caa6ace6a0fb498973a24a47e5bdecc601e067daaf4 0.600000000000 1516175 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": 1046374, "vin": [ { "gen": { "height": 1046364 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e78037a5410b966e4486caa6ace6a0fb498973a24a47e5bdecc601e067daaf4" } } ], "extra": [ 1, 196, 225, 109, 154, 56, 185, 6, 245, 236, 136, 252, 72, 40, 181, 211, 36, 78, 86, 73, 177, 247, 44, 172, 251, 179, 176, 170, 103, 145, 9, 225, 144, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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