Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43bc0f90c26aad02736a64888f3fca02da82e7b2b819cf4001f7fe9df59bda18

Tx prefix hash: 659aaa7958246ee664603d2df50c51854cc2dc6a38177c5e7ae741f7752a2ad7
Tx public key: 236e4e1fce02f608011b85367e978ef9e0f57f7019acf8ffc08dcc635c406323
Timestamp: 1724072089 Timestamp [UCT]: 2024-08-19 12:54:49 Age [y:d:h:m:s]: 00:282:09:06:31
Block: 1091317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201724 RingCT/type: yes/0
Extra: 01236e4e1fce02f608011b85367e978ef9e0f57f7019acf8ffc08dcc635c40632302110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a109bc61d8a8ac999b4303934461e052de33b56214d3fd1f45a5d438c203e2b6 0.600000000000 1565948 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": 1091327, "vin": [ { "gen": { "height": 1091317 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a109bc61d8a8ac999b4303934461e052de33b56214d3fd1f45a5d438c203e2b6" } } ], "extra": [ 1, 35, 110, 78, 31, 206, 2, 246, 8, 1, 27, 133, 54, 126, 151, 142, 249, 224, 245, 127, 112, 25, 172, 248, 255, 192, 141, 204, 99, 92, 64, 99, 35, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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