Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a4867d8074f63677534432ce32e916f32fe8f4dd8bdb7fff7baab270e63619d

Tx prefix hash: 3fdb2f54390f45986a64df4885f603e747ca92bec793b8fc7cddb86d2157169f
Tx public key: 0477ff7b097f37af89c85f045e92ae426667d5c0fc795054a97e7d56406f1e5d
Timestamp: 1724278164 Timestamp [UCT]: 2024-08-21 22:09:24 Age [y:d:h:m:s]: 01:074:11:12:02
Block: 1093031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311663 RingCT/type: yes/0
Extra: 010477ff7b097f37af89c85f045e92ae426667d5c0fc795054a97e7d56406f1e5d021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6fbd7d4acc9a11c0d59e83b9373982d5ae108e6dce7f6e9b793140d1981fa441 0.600000000000 1567894 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": 1093041, "vin": [ { "gen": { "height": 1093031 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6fbd7d4acc9a11c0d59e83b9373982d5ae108e6dce7f6e9b793140d1981fa441" } } ], "extra": [ 1, 4, 119, 255, 123, 9, 127, 55, 175, 137, 200, 95, 4, 94, 146, 174, 66, 102, 103, 213, 192, 252, 121, 80, 84, 169, 126, 125, 86, 64, 111, 30, 93, 2, 17, 0, 0, 0, 2, 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