Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a5fba7c766757ca6a6b4b34c43dbeaf627fe937ef75a7a4ceaa24d324b9395f

Tx prefix hash: 58a3041b0a5e059915aa2ee190bca1ce8e93f81ed74beed14260642f77954a51
Tx public key: fcfe3d4969ccd2f396365337120086c187f74cfeb4d90f46dae88812604d6aa2
Timestamp: 1717577648 Timestamp [UCT]: 2024-06-05 08:54:08 Age [y:d:h:m:s]: 01:162:00:24:48
Block: 1037473 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374378 RingCT/type: yes/0
Extra: 01fcfe3d4969ccd2f396365337120086c187f74cfeb4d90f46dae88812604d6aa202110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ee79b4752b8f53a27fc22a6e6c8a244f22b6ad9e15e7a416b8baf0fcd08ddb0 0.600000000000 1506014 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": 1037483, "vin": [ { "gen": { "height": 1037473 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ee79b4752b8f53a27fc22a6e6c8a244f22b6ad9e15e7a416b8baf0fcd08ddb0" } } ], "extra": [ 1, 252, 254, 61, 73, 105, 204, 210, 243, 150, 54, 83, 55, 18, 0, 134, 193, 135, 247, 76, 254, 180, 217, 15, 70, 218, 232, 136, 18, 96, 77, 106, 162, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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