Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 233b3dccebd592298c6fa6b0d6aa4ab0f16ba57bd216e7eee26da4025479729b

Tx prefix hash: f6e49dffebcf44b638bd39d18c2d59c5cc48c889a0404ff76f45957fe68e38b7
Tx public key: 81c478c18e1e358b3ef8793c7d6358fb71f76f6a445da6d87c49eff0ef87e24b
Timestamp: 1715730943 Timestamp [UCT]: 2024-05-14 23:55:43 Age [y:d:h:m:s]: 00:329:04:29:10
Block: 1022167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235287 RingCT/type: yes/0
Extra: 0181c478c18e1e358b3ef8793c7d6358fb71f76f6a445da6d87c49eff0ef87e24b021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17f81a875ec873513cf2dc1da12949d06cf633407840ed32c03b693f56379218 0.600000000000 1486688 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": 1022177, "vin": [ { "gen": { "height": 1022167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17f81a875ec873513cf2dc1da12949d06cf633407840ed32c03b693f56379218" } } ], "extra": [ 1, 129, 196, 120, 193, 142, 30, 53, 139, 62, 248, 121, 60, 125, 99, 88, 251, 113, 247, 111, 106, 68, 93, 166, 216, 124, 73, 239, 240, 239, 135, 226, 75, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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