Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d74548bc6476990dbea765b6aaf355f126552135facef7733539488a9cbf7ca

Tx prefix hash: 44af8aca41d55f3e45adf8ddf5cd9e7956ecd25c083552d031eb3f9cf6973bb1
Tx public key: c0f79d9a22910db920c1d20c051c84e573601c6b1e03c5b0ddc4620bba4b4d51
Timestamp: 1707724075 Timestamp [UCT]: 2024-02-12 07:47:55 Age [y:d:h:m:s]: 01:127:17:00:56
Block: 955776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352232 RingCT/type: yes/0
Extra: 01c0f79d9a22910db920c1d20c051c84e573601c6b1e03c5b0ddc4620bba4b4d5102110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f8aace167a3bf12310dcbeb9ce2dc6882c0324e00a2c1bc874a7e1ec9e86980 0.600000000000 1415076 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": 955786, "vin": [ { "gen": { "height": 955776 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f8aace167a3bf12310dcbeb9ce2dc6882c0324e00a2c1bc874a7e1ec9e86980" } } ], "extra": [ 1, 192, 247, 157, 154, 34, 145, 13, 185, 32, 193, 210, 12, 5, 28, 132, 229, 115, 96, 28, 107, 30, 3, 197, 176, 221, 196, 98, 11, 186, 75, 77, 81, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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