Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 287c837257ff98c1046d458fe01e26baf7e8f869d1e0f4a1415d73fc2369d2ed

Tx prefix hash: d34fbcdde22292a0b954ae09ad1a8233e3f3cea1e5d1c8cdd7c1ee6452f2bcb3
Tx public key: 41d5ba465ac115624868e2b338748f5de70d76f8930eb43a5f50c859b5013d6f
Timestamp: 1721043016 Timestamp [UCT]: 2024-07-15 11:30:16 Age [y:d:h:m:s]: 00:193:08:48:23
Block: 1066216 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138293 RingCT/type: yes/0
Extra: 0141d5ba465ac115624868e2b338748f5de70d76f8930eb43a5f50c859b5013d6f02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 58d24d00f282fc029ff519f3dc0ccdeb08dbb65e828a489e577517b3fecf91d7 0.600000000000 1536789 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": 1066226, "vin": [ { "gen": { "height": 1066216 } } ], "vout": [ { "amount": 600000000, "target": { "key": "58d24d00f282fc029ff519f3dc0ccdeb08dbb65e828a489e577517b3fecf91d7" } } ], "extra": [ 1, 65, 213, 186, 70, 90, 193, 21, 98, 72, 104, 226, 179, 56, 116, 143, 93, 231, 13, 118, 248, 147, 14, 180, 58, 95, 80, 200, 89, 181, 1, 61, 111, 2, 17, 0, 0, 0, 1, 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