Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9313ba3e198e6aca095f16596f5924f742fbca6def1a6931763058fe06639c6

Tx prefix hash: 86c618377752ff0fc833ce27d4617ed99b46fab24e0777437c4ebed04194f380
Tx public key: 73963cca084a017ca30ba6b27f7a24226a07b72c576d0f8e44c7df06d143e5c1
Timestamp: 1706855054 Timestamp [UCT]: 2024-02-02 06:24:14 Age [y:d:h:m:s]: 01:027:18:57:11
Block: 948573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280886 RingCT/type: yes/0
Extra: 0173963cca084a017ca30ba6b27f7a24226a07b72c576d0f8e44c7df06d143e5c102110000000310a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86a7f5db8258d2ec6c138f6f62f7e6daf5e95dcfd1bd021883ba86bb9893b68f 0.600000000000 1407007 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": 948583, "vin": [ { "gen": { "height": 948573 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86a7f5db8258d2ec6c138f6f62f7e6daf5e95dcfd1bd021883ba86bb9893b68f" } } ], "extra": [ 1, 115, 150, 60, 202, 8, 74, 1, 124, 163, 11, 166, 178, 127, 122, 36, 34, 106, 7, 183, 44, 87, 109, 15, 142, 68, 199, 223, 6, 209, 67, 229, 193, 2, 17, 0, 0, 0, 3, 16, 161, 116, 143, 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