Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4b6c849ce0d92c48e945d83e964154031fd9e4218e8514e1694d576d2b5f1b0

Tx prefix hash: 1c48142a1b58c420c9c619171ad1f569df6dcfd5a79498bb7f378359750a31fe
Tx public key: 50bed93850e90fe05a532b762102e2253b249b392266dd4b90aae40a31a9cc90
Timestamp: 1678158052 Timestamp [UCT]: 2023-03-07 03:00:52 Age [y:d:h:m:s]: 01:354:19:24:10
Block: 711563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 514238 RingCT/type: yes/0
Extra: 0150bed93850e90fe05a532b762102e2253b249b392266dd4b90aae40a31a9cc9002110000000e5029cbac000000000000000000

1 output(s) for total of 2.693371706000 dcy

stealth address amount amount idx
00: 66bcd4890c183aff291cb32a404a9275923d3d87d3ff57dee4dc76583b20e541 2.693371706000 1155696 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": 711573, "vin": [ { "gen": { "height": 711563 } } ], "vout": [ { "amount": 2693371706, "target": { "key": "66bcd4890c183aff291cb32a404a9275923d3d87d3ff57dee4dc76583b20e541" } } ], "extra": [ 1, 80, 190, 217, 56, 80, 233, 15, 224, 90, 83, 43, 118, 33, 2, 226, 37, 59, 36, 155, 57, 34, 102, 221, 75, 144, 170, 228, 10, 49, 169, 204, 144, 2, 17, 0, 0, 0, 14, 80, 41, 203, 172, 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