Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a055a5bd7d6d16af657e8549c1c00de9f02caba08bc0afd3221d64c8c6a6ffcb

Tx prefix hash: ef70f8541f517162621ffa93aab881ebdbf617c11cc2b45983c0d4998938f36c
Tx public key: 879baecd3675f5592a17dd8682ebb5bdcc67b06bce5c850b519d9ee40d818c3c
Timestamp: 1707879605 Timestamp [UCT]: 2024-02-14 03:00:05 Age [y:d:h:m:s]: 01:073:18:48:59
Block: 957059 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313802 RingCT/type: yes/0
Extra: 01879baecd3675f5592a17dd8682ebb5bdcc67b06bce5c850b519d9ee40d818c3c02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05ed8d284f0b1f7a40fd892d1e97584daca5f73fe46b7c03189ca3d3352d01b2 0.600000000000 1416373 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": 957069, "vin": [ { "gen": { "height": 957059 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05ed8d284f0b1f7a40fd892d1e97584daca5f73fe46b7c03189ca3d3352d01b2" } } ], "extra": [ 1, 135, 155, 174, 205, 54, 117, 245, 89, 42, 23, 221, 134, 130, 235, 181, 189, 204, 103, 176, 107, 206, 92, 133, 11, 81, 157, 158, 228, 13, 129, 140, 60, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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