Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f7b42898c9f3bd815e4c62c68b6e48774ea34867d274a34c94a1cf2244162e0

Tx prefix hash: 68d9015583be20e36df06411b7f1da4f86e5b0acb44f6432da2d7151c3ae50a1
Tx public key: f7e3414440fbf1a3762154d3b88818cbdaf6fbf8a80691680879ce61e8bced5a
Timestamp: 1708938469 Timestamp [UCT]: 2024-02-26 09:07:49 Age [y:d:h:m:s]: 01:046:16:08:40
Block: 965860 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294359 RingCT/type: yes/0
Extra: 01f7e3414440fbf1a3762154d3b88818cbdaf6fbf8a80691680879ce61e8bced5a0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2050a3842ac66a36d3ff42fa0fd577997c997ca5cac5944c26c164f2c195cbb0 0.600000000000 1425615 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": 965870, "vin": [ { "gen": { "height": 965860 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2050a3842ac66a36d3ff42fa0fd577997c997ca5cac5944c26c164f2c195cbb0" } } ], "extra": [ 1, 247, 227, 65, 68, 64, 251, 241, 163, 118, 33, 84, 211, 184, 136, 24, 203, 218, 246, 251, 248, 168, 6, 145, 104, 8, 121, 206, 97, 232, 188, 237, 90, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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