Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f00e7e0f830a4f2a1f25a60eda1c42c0a3db3f8dea070ea40615397f91a2782

Tx prefix hash: 4598f0029450ac15e4f8b34e46f543c255509906ed94328a695dddd518cbfd4f
Tx public key: 295ac47655cf064cccaf9fcca3a09d92219aa60cfb3e44087d70b16292038975
Timestamp: 1672941740 Timestamp [UCT]: 2023-01-05 18:02:20 Age [y:d:h:m:s]: 02:108:23:02:03
Block: 668278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 599570 RingCT/type: yes/0
Extra: 01295ac47655cf064cccaf9fcca3a09d92219aa60cfb3e44087d70b1629203897502110000000152542ceb000000000000000000

1 output(s) for total of 3.747291952000 dcy

stealth address amount amount idx
00: 3067fa78f0e9b7cc53234e3d65b39e3c28630986b3ab1fdf474c7d2a29c8db0f 3.747291952000 1109519 of 0

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": 668288, "vin": [ { "gen": { "height": 668278 } } ], "vout": [ { "amount": 3747291952, "target": { "key": "3067fa78f0e9b7cc53234e3d65b39e3c28630986b3ab1fdf474c7d2a29c8db0f" } } ], "extra": [ 1, 41, 90, 196, 118, 85, 207, 6, 76, 204, 175, 159, 204, 163, 160, 157, 146, 33, 154, 166, 12, 251, 62, 68, 8, 125, 112, 177, 98, 146, 3, 137, 117, 2, 17, 0, 0, 0, 1, 82, 84, 44, 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