Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8a215d8d1767bf868495bf976cb99781caee43d6ad60449cb75097f879bcc7a

Tx prefix hash: dade080319860b3d53667600d5d49a6c2175ad973c39428615dcaf50e3e0f5c4
Tx public key: eb69b870f392087a9f2fb1e5cce9f77b26518a325a1ffcbe768669b7e4245fea
Timestamp: 1724998261 Timestamp [UCT]: 2024-08-30 06:11:01 Age [y:d:h:m:s]: 00:230:23:47:07
Block: 1098994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164953 RingCT/type: yes/0
Extra: 01eb69b870f392087a9f2fb1e5cce9f77b26518a325a1ffcbe768669b7e4245fea021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b233b7fe4c060563d29c9381824d90ae2ff04af26745e2a29d6c989ea70d5889 0.600000000000 1574901 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": 1099004, "vin": [ { "gen": { "height": 1098994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b233b7fe4c060563d29c9381824d90ae2ff04af26745e2a29d6c989ea70d5889" } } ], "extra": [ 1, 235, 105, 184, 112, 243, 146, 8, 122, 159, 47, 177, 229, 204, 233, 247, 123, 38, 81, 138, 50, 90, 31, 252, 190, 118, 134, 105, 183, 228, 36, 95, 234, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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