Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3584602b3d352e57c4bd5f134ccc2f5d0f9314ba5480f5ec0bb159b018e077e

Tx prefix hash: 9e5036b11aaec0db9f15d7a791d2d321d8217c9799e8ba7b4b861c7de91adf29
Tx public key: 58781de31d6497e5daa9dc66e191ca65361f454b28256c8f8c14ae616868a919
Timestamp: 1704379915 Timestamp [UCT]: 2024-01-04 14:51:55 Age [y:d:h:m:s]: 01:335:10:16:50
Block: 928060 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498591 RingCT/type: yes/0
Extra: 0158781de31d6497e5daa9dc66e191ca65361f454b28256c8f8c14ae616868a91902110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a285c4982d6b0fb2bd1ef88242d580cec26a69c0bd5a9a89bc4a6609653c2f1 0.600000000000 1385916 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": 928070, "vin": [ { "gen": { "height": 928060 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a285c4982d6b0fb2bd1ef88242d580cec26a69c0bd5a9a89bc4a6609653c2f1" } } ], "extra": [ 1, 88, 120, 29, 227, 29, 100, 151, 229, 218, 169, 220, 102, 225, 145, 202, 101, 54, 31, 69, 75, 40, 37, 108, 143, 140, 20, 174, 97, 104, 104, 169, 25, 2, 17, 0, 0, 0, 10, 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