Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fdb2c3824e7dad13590eacb905f3361aabf751f4169dd71e9a7720412e131ad

Tx prefix hash: 1041456d123f3308cb1f447b9c05a68b6d402297cb9132292e9e401b35b0e8c9
Tx public key: a9163df926f8b0a1e5f82b314dc5fe079a4d3bccddf4addcff41e8237c69e545
Timestamp: 1729084528 Timestamp [UCT]: 2024-10-16 13:15:28 Age [y:d:h:m:s]: 00:147:22:07:38
Block: 1132891 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105485 RingCT/type: yes/0
Extra: 01a9163df926f8b0a1e5f82b314dc5fe079a4d3bccddf4addcff41e8237c69e5450211000000073cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d53bde2954db35935e0f02a153393a8255d0ab51f493a28abc42c4ea4bf0d0f 0.600000000000 1615916 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": 1132901, "vin": [ { "gen": { "height": 1132891 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d53bde2954db35935e0f02a153393a8255d0ab51f493a28abc42c4ea4bf0d0f" } } ], "extra": [ 1, 169, 22, 61, 249, 38, 248, 176, 161, 229, 248, 43, 49, 77, 197, 254, 7, 154, 77, 59, 204, 221, 244, 173, 220, 255, 65, 232, 35, 124, 105, 229, 69, 2, 17, 0, 0, 0, 7, 60, 208, 252, 6, 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