Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11f5d344804739857d54b1d42865652d9ff3a978645c38c4556a89a9efc1d33d

Tx prefix hash: d80364552eb3c624258f8fb826255e283ddf2e8f97010edf51597cbed59d157c
Tx public key: 919c89f2d21fa14d9288c852b2c5f6fc053c5dac83692ccc875d7846d9246244
Timestamp: 1729631989 Timestamp [UCT]: 2024-10-22 21:19:49 Age [y:d:h:m:s]: 00:000:08:58:54
Block: 1137375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268 RingCT/type: yes/0
Extra: 01919c89f2d21fa14d9288c852b2c5f6fc053c5dac83692ccc875d7846d9246244021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7efc7e5a3ecb3611e0520ee1bd1c4c58fc4b00967e77a4f000d338cb2f8f0d3 0.600000000000 1620854 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": 1137385, "vin": [ { "gen": { "height": 1137375 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7efc7e5a3ecb3611e0520ee1bd1c4c58fc4b00967e77a4f000d338cb2f8f0d3" } } ], "extra": [ 1, 145, 156, 137, 242, 210, 31, 161, 77, 146, 136, 200, 82, 178, 197, 246, 252, 5, 60, 93, 172, 131, 105, 44, 204, 135, 93, 120, 70, 217, 36, 98, 68, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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