Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2a2d21bb64f834de423c3d94e8b77f8d2ad4c3b347099da4b65f1af588096c0

Tx prefix hash: 00f3931e953a3fa495d2139580554e0eebd29afc98d9a0556dee3194f93778fc
Tx public key: 93ea7c84ef1db9ab16f01b7e7160d294761ce716af072601431021c0d849515b
Timestamp: 1721714824 Timestamp [UCT]: 2024-07-23 06:07:04 Age [y:d:h:m:s]: 00:253:01:31:56
Block: 1071760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180783 RingCT/type: yes/0
Extra: 0193ea7c84ef1db9ab16f01b7e7160d294761ce716af072601431021c0d849515b02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 690c92186adb7339dd73cc5c3f595b0e1a1f1656d625c6f5da9dff93e4a38385 0.600000000000 1544107 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": 1071770, "vin": [ { "gen": { "height": 1071760 } } ], "vout": [ { "amount": 600000000, "target": { "key": "690c92186adb7339dd73cc5c3f595b0e1a1f1656d625c6f5da9dff93e4a38385" } } ], "extra": [ 1, 147, 234, 124, 132, 239, 29, 185, 171, 22, 240, 27, 126, 113, 96, 210, 148, 118, 28, 231, 22, 175, 7, 38, 1, 67, 16, 33, 192, 216, 73, 81, 91, 2, 17, 0, 0, 0, 7, 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