Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 848285dcfd468f392f3a687eafec1226af6cac5e2c8ad5753f827d827e67e48e

Tx prefix hash: 31e441b2ebf89306e657aca7a9b9a1c5e4a45d5c6fe5ea8ce92ccbbc666e00c1
Tx public key: 2628d24541df002b4a758e86c708fe0e979a67c2b609758ec31712555bcfa862
Timestamp: 1705565016 Timestamp [UCT]: 2024-01-18 08:03:36 Age [y:d:h:m:s]: 01:079:18:34:29
Block: 937857 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318101 RingCT/type: yes/0
Extra: 012628d24541df002b4a758e86c708fe0e979a67c2b609758ec31712555bcfa86202110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c68ab3519a15a4894a59cb8a0136e553da5c57b593039f2dcd72fec624b9aaf7 0.600000000000 1395921 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": 937867, "vin": [ { "gen": { "height": 937857 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c68ab3519a15a4894a59cb8a0136e553da5c57b593039f2dcd72fec624b9aaf7" } } ], "extra": [ 1, 38, 40, 210, 69, 65, 223, 0, 43, 74, 117, 142, 134, 199, 8, 254, 14, 151, 154, 103, 194, 182, 9, 117, 142, 195, 23, 18, 85, 91, 207, 168, 98, 2, 17, 0, 0, 0, 1, 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