Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0f8ed8092ae388f562595d42e0f997ca822964e22ae7c11529ebd46d209c9a5

Tx prefix hash: f772434cd5207a05cf4d908aa3ecd9dc76a8980700dec4958cfbb7b283d9bb05
Tx public key: 9ce2c54d3bd24ba6dfd200338de77914ae89510d410906173b21f46e2f748be3
Timestamp: 1638149559 Timestamp [UCT]: 2021-11-29 01:32:39 Age [y:d:h:m:s]: 03:029:02:27:40
Block: 384334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 799703 RingCT/type: yes/0
Extra: 019ce2c54d3bd24ba6dfd200338de77914ae89510d410906173b21f46e2f748be30211000000091cab2639000000000000000000

1 output(s) for total of 32.699588524000 dcy

stealth address amount amount idx
00: 3fe42b0c16cf5a9cc7ad638516061d0c8f016b69fcc0fbd402cd9eadc30e60cb 32.699588524000 775765 of 0

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": 384344, "vin": [ { "gen": { "height": 384334 } } ], "vout": [ { "amount": 32699588524, "target": { "key": "3fe42b0c16cf5a9cc7ad638516061d0c8f016b69fcc0fbd402cd9eadc30e60cb" } } ], "extra": [ 1, 156, 226, 197, 77, 59, 210, 75, 166, 223, 210, 0, 51, 141, 231, 121, 20, 174, 137, 81, 13, 65, 9, 6, 23, 59, 33, 244, 110, 47, 116, 139, 227, 2, 17, 0, 0, 0, 9, 28, 171, 38, 57, 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