Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16ff83cfc38d4ab7fd624e46591d4d917a6e6f87f021427dec48cf239a5070f2

Tx prefix hash: 2309f562c934468b1eaf7bdea38f2d757985afca83fb87469b04e4ccbb7d0074
Tx public key: 9264a8fb782c55203bcc806d71d1c08ba3e45f660f0774b897700bb03ef2d7ea
Timestamp: 1740197543 Timestamp [UCT]: 2025-02-22 04:12:23 Age [y:d:h:m:s]: 00:271:17:32:18
Block: 1224530 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191981 RingCT/type: yes/0
Extra: 019264a8fb782c55203bcc806d71d1c08ba3e45f660f0774b897700bb03ef2d7ea0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f21def723e9de6701ddfa5155e4b5807cd6333a2ae61e448f368f84d5a78529e 0.600000000000 1711393 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": 1224540, "vin": [ { "gen": { "height": 1224530 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f21def723e9de6701ddfa5155e4b5807cd6333a2ae61e448f368f84d5a78529e" } } ], "extra": [ 1, 146, 100, 168, 251, 120, 44, 85, 32, 59, 204, 128, 109, 113, 209, 192, 139, 163, 228, 95, 102, 15, 7, 116, 184, 151, 112, 11, 176, 62, 242, 215, 234, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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