Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 190818f33b2068e08bba58fd1f926784c0765dca3afe80842cab751d3760c6f9

Tx prefix hash: 484943b2acb2f1b907fd175a86adb149d35c58a11423ce447e937b6bb8c76f3a
Tx public key: 3c994617726387f815f80f9469d12fed87653ef73f5ea0976dc122c2c2db7bfc
Timestamp: 1707946468 Timestamp [UCT]: 2024-02-14 21:34:28 Age [y:d:h:m:s]: 01:121:13:54:42
Block: 957614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347889 RingCT/type: yes/0
Extra: 013c994617726387f815f80f9469d12fed87653ef73f5ea0976dc122c2c2db7bfc0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a7feedad8c9ade3e538d0e7a02752ed7cc9002e0e3d81749a248beacf72953b 0.600000000000 1416934 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": 957624, "vin": [ { "gen": { "height": 957614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a7feedad8c9ade3e538d0e7a02752ed7cc9002e0e3d81749a248beacf72953b" } } ], "extra": [ 1, 60, 153, 70, 23, 114, 99, 135, 248, 21, 248, 15, 148, 105, 209, 47, 237, 135, 101, 62, 247, 63, 94, 160, 151, 109, 193, 34, 194, 194, 219, 123, 252, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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